Methods for resource configuration for transmission in inactive state

ABSTRACT

Some aspects of the present disclosure introduce a new downlink (DL) bandwidth part (BWP) and a new uplink (UL) BWP for communication in the RRC_INACTIVE state. In addition, aspects of the disclosure also provide for configuring generic parameters of the BWP, which include, but not limited to, frequency location, bandwidth, subcarrier spacing (SCS), and cyclic prefix (CP). Some aspects of the present disclosure may support a reinterpretation of generic parameters of a BWP, for example which may be configured for the RRC_CONNECTED state, to be used in the RRC_INACTIVE state. Some aspects of the present disclosure are directed to implicit DL BWP switching in the RRC_INACTIVE state where no BWP identifier (ID) indication is needed as part of the switching mechanism.

RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 16/664,340 filed on Oct. 25, 2019, which isincorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates generally to wireless communications, andin particular embodiments, to control signaling in wirelesscommunication networks.

BACKGROUND

In some wireless communication networks, user equipments (UEs)wirelessly communicate with a base station to send data to the basestation and/or receive data from the base station. A wirelesscommunication from a UE to a base station is referred to as an uplink(UL) communication. A wireless communication from a base station to a UEis referred to as a downlink (DL) communication. A wirelesscommunication from a first UE to a second UE is referred to as asidelink (SL) communication or a device-to-device (D2D) communication.

In 3GPP New Radio (NR), a UE may operate in one of the following threestates: RRC_IDLE, RRC_CONNECTED and RRC_INACTIVE. In the RRC_CONNECTEDstate, a UE is connected to the network following a connectionestablishment procedure. In the RRC_IDLE state, a UE is not connected tothe network, but the network knows that the UE is present in thenetwork. Switching to the RRC_IDLE state helps save network resourcesand UE power (for example, battery life) when the UE is notcommunicating with the network. The RRC_INACTIVE state also helps savenetwork resources and UE power when the UE is not communicating with thenetwork. However, unlike the RRC_IDLE state, when a UE is in theRRC_INACTIVE state the network and the UE both store at least someconfiguration information to allow the UE to reconnect to the networkmore rapidly.

Improved mechanisms for operation in the RRC_INACTIVE state would bebeneficial for communication systems.

SUMMARY

According to a first aspect of the disclosure, there is provided amethod involving, while in a radio resource control (RRC)_CONNECTEDstate, a user equipment (UE) determining configuration information forconfiguring a bandwidth part (BWP) for communication in an RRC_INACTIVEstate. The method also involves the UE entering the RRC_INACTIVE stateand the UE using the configured BWP for communication in theRRC_INACTIVE state.

In some embodiments, determining configuration information forconfiguring the BWP for communication in the RRC_INACTIVE state involvesreceiving the configuration information.

In some embodiments, the configuration information explicitly definesBWP parameters for the configured BWP for communication in theRRC_INACTIVE state.

In some embodiments, the configuration information indicates a BWPidentifier that identifies a previously configured BWP that will be usedfor communication in the RRC_INACTIVE state.

In some embodiments, the configuration information indicates that theconfigured BWP is a last active BWP of the UE in the RRC_CONNECTED statebefore the UE enters the RRC_INACTIVE state.

In some embodiments, the method further involves, when in theRRC_INACTIVE state, receiving downlink control information that includesscheduling information.

In some embodiments, the scheduling information includes: schedulinginformation for receiving downlink data while in the RRC_INACTIVE state;or scheduling information for receiving paging information that includesscheduling information for receiving downlink data while in theRRC_INACTIVE state.

In some embodiments, the configured BWP for communication in theRRC_INACTIVE state involves the UE transmitting uplink data in theconfigured BWP for communication in the RRC_INACTIVE state.

In some embodiments, the configuration information for configuring theBWP for communication in the RRC_INACTIVE state includes an extendedcyclic prefix (CP).

In some embodiments, the extended CP is for an uplink BWP.

In some embodiments, the method further involves, when in theRRC_INACTIVE state, switching to the configured BWP for communication inthe RRC_INACTIVE state.

In some embodiments, the switching occurs when a pre-defined conditionis met,

In some embodiments, the pre-defined condition is one of: the configuredBWP for communication in the RRC_INACTIVE state has a differentfrequency location and bandwidth or a different sub-carrier spacing(SCS) or a different cyclic prefix (CP) than control resource set 0(CORESET 0); or the configured BWP for communication in the RRC_INACTIVEstate does not include all resource blocks of CORESET 0 or has adifferent SCS or a different CP than CORESET 0.

In some embodiments, the method further involves, when in theRRC_INACTIVE state, switching to control resource set 0 (CORESET 0) fromthe configured BWP for communication in the RRC_INACTIVE state.

According to a second aspect of the disclosure, there is provided a userequipment (UE) including a processor and a computer-readable storagemedia having stored thereon, computer executable instructions. Whenexecuted by the processor, the computer executable instructions causethe UE to: while in a radio resource control (RRC)_CONNECTED state,determine configuration information for configuring a bandwidth part(BWP) for communication in a RRC_INACTIVE state; enter the RRC_INACTIVEstate; and use the configured BWP for communication in the RRC_INACTIVEstate.

In some embodiments, the computer executable instructions to determineconfiguration information for configuring the BWP for communication inthe RRC_INACTIVE state comprise computer executable instructions toreceive the configuration information.

In some embodiments, the configuration information explicitly definesBWP parameters for the configured BWP for communication in theRRC_INACTIVE state.

In some embodiments, the configuration information indicates a BWPidentifier that identifies a previously configured BWP that will be usedfor communication in the RRC_INACTIVE state.

In some embodiments, the configuration information indicates that theconfigured BWP for communication in the RRC_INACTIVE state is a lastactive BWP of the UE in the RRC_CONNECTED state before the UE enters theRRC_INACTIVE state.

In some embodiments, when in the RRC_INACTIVE state, the computerreadable instructions when executed by the processor cause the UE toreceive downlink control information that includes schedulinginformation.

In some embodiments, the scheduling information includes: schedulinginformation for receiving downlink data while in the RRC_INACTIVE state;or scheduling information for receiving paging information that includesscheduling information for receiving downlink data while in theRRC_INACTIVE state.

In some embodiments, the computer executable instructions to use theconfigured BWP for communication in the RRC_INACTIVE state comprisecomputer executable instructions to transmit uplink data in theconfigured BWP for communication in the RRC_INACTIVE state.

In some embodiments, the configuration information for configuring theBWP for communication in the RRC_INACTIVE state includes an extendedcyclic prefix (CP), wherein the extended CP is for an uplink BWP.

In some embodiments, when in the RRC_INACTIVE state, the computerreadable instructions when executed by the processor cause the UE toswitch to the configured BWP for communication in the RRC_INACTIVEstate.

In some embodiments, the switching occurs when a pre-defined conditionis met, wherein the pre-defined condition is one of: the configured BWPfor communication in the RRC_INACTIVE state has a different frequencylocation and bandwidth or a different sub-carrier spacing (SCS) or adifferent cyclic prefix (CP) than control resource set 0 (CORESET 0); orthe configured BWP for communication in the RRC_INACTIVE state does notinclude all resource blocks of CORESET 0 or has a different SCS or adifferent CP than CORESET 0.

In some embodiments, when in the RRC_INACTIVE state, the computerreadable instructions when executed by the processor cause the UE toswitch to control resource set 0 (CORESET 0) from the configured BWP forcommunication in the RRC_INACTIVE state.

According to a third aspect of the disclosure, there is provided amethod involving a network side device determining configurationinformation for configuring a bandwidth part (BWP) for communication inan RRC_INACTIVE state. The method further involves the network sidedevice transmitting signalling indicating a suspension of a radioresource control (RRC)_CONNECTED state resulting in a user equipment(UE) entering the RRC_INACTIVE state. The method further involves thenetwork side device using the configured BWP for the RRC_INACTIVE statefor communication with the UE when the UE is in the RRC_INACTIVE state.

In some embodiments, the method further involves the network side devicetransmitting the configuration information for configuring theRRC_INACTIVE state BWP for use by the UE for communication in theRRC_INACTIVE state.

In some embodiments, the configuration information explicitly definesBWP parameters for the configured BWP for communication in theRRC_INACTIVE state.

In some embodiments, the configuration information indicates a BWPidentifier that identifies a previously configured BWP that will be usedfor communication in the RRC_INACTIVE state.

In some embodiments, the configuration information indicates that theconfigured BWP is a last active BWP of the UE in the RRC_CONNECTED statebefore the UE enters the RRC_INACTIVE state.

In some embodiments, the method further involves, when the UE is in theRRC_INACTIVE state, transmitting downlink control information thatincludes scheduling information.

In some embodiments, the scheduling information includes: schedulinginformation for receiving downlink data while in the RRC_INACTIVE state;or scheduling information for receiving paging information that includesscheduling information for receiving downlink data while in theRRC_INACTIVE state.

In some embodiments, using the configured BWP for communication in theRRC_INACTIVE state involves the network side device receiving uplinkdata in the configured BWP for communication in the RRC_INACTIVE state.

In some embodiments, the configuration information for configuring theBWP for communication in the RRC_INACTIVE state includes an extendedcyclic prefix (CP).

In some embodiments, the extended cyclic prefix (CP) is for an uplinkBWP.

In some embodiments, the method further involves, when the UE is in theRRC_INACTIVE state, the network side device using control resource set 0(CORESET 0) for communication in the RRC_INACTIVE state.

According to a fourth aspect of the disclosure, there is provided anetwork device including a processor and a computer-readable storagemedia having stored thereon computer executable instructions. Whenexecuted by the processor, the computer executable instructions causethe network device to: determine configuration information forconfiguring a bandwidth part (BWP) for communication in an RRC_INACTIVEstate; transmit signalling indicating a suspension of a radio resourcecontrol (RRC)_CONNECTED state resulting in a user equipment (UE)entering the RRC_INACTIVE state; and use the BWP configured forRRC_INACTIVE state for communication with the UE when the UE is in theRRC_INACTIVE state.

In some embodiments, the computer executable instructions when executedby the processor cause the network side device to transmitting theconfiguration information for configuring the RRC_INACTIVE state BWP foruse by the UE for communication in the RRC_INACTIVE state.

In some embodiments, the configuration information explicitly definesBWP parameters for the configured BWP for communication in theRRC_INACTIVE state.

In some embodiments, the configuration information indicates a BWPidentifier that identifies a previously configured BWP that will be usedfor communication in the RRC_INACTIVE state.

In some embodiments, the configuration information indicates that theconfigured BWP for communication in the RRC_INACTIVE state is a lastactive BWP of the UE in the RRC_CONNECTED state before the UE enters theRRC_INACTIVE state.

In some embodiments, when in the RRC_INACTIVE state, the computerreadable instructions when executed by the processor cause the networkside device to transmit downlink control information that includesscheduling information.

In some embodiments, the scheduling information includes: schedulinginformation for the UE to receive downlink data while in theRRC_INACTIVE state; or scheduling information for the UE to receivepaging information that includes scheduling information for receivingdownlink data while in the RRC_INACTIVE state.

In some embodiments, the computer executable instructions when executedby the processor cause the network side device to use the configured BWPfor communication in the RRC_INACTIVE state comprise computer executableinstructions to receive uplink data in the configured BWP forcommunication in the RRC_INACTIVE state.

In some embodiments, the configuration information for configuring theBWP for communication in the RRC_INACTIVE state includes an extendedcyclic prefix (CP), wherein the extended CP is for an uplink BWP.

In some embodiments, when in the RRC_INACTIVE state, the computerreadable instructions when executed by the processor cause the networkside device to use control resource set 0 (CORESET 0) for communicationin the RRC_INACTIVE state.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present embodiments, and theadvantages thereof, reference is now made, by way of example, to thefollowing descriptions taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a schematic diagram of a communication system in whichembodiments of the disclosure may occur;

FIGS. 2A and 2B are block diagrams of an example user equipment and basestation, respectively, according to aspects of the present disclosure;

FIG. 3 is a block diagram of an air interface manager for configuring asoftware-configurable air interface according to an aspect of thepresent disclosure;

FIGS. 4A to 4D illustrate four different examples of the configuredINACTIVE DL BWP following a transition from the RRC_CONNECTED state toRRC_INACTIVE state, according to aspects of the present disclosure;

FIGS. 5A to 5C illustrate four different examples of the configuredINACTIVE DL BWP following a transition from the RRC_CONNECTED state toRRC_INACTIVE state, according to aspects of the present disclosure.

FIG. 6A illustrates an example of when a condition for DL BWP switchingis met in the RRC_INACTIVE state, according to aspects of the presentdisclosure.

FIG. 6B illustrates an example of when a condition for DL BWP switchingis not met in the RRC_INACTIVE state, according to aspects of thepresent disclosure.

FIG. 7 is a signaling flow diagram showing signaling for DCI-based DLdata scheduling that occurs between a UE and base station when the UE isinitially in an RRC_CONNECTED state and when the UE is released andenters an RRC_INACTIVE state, according to aspects of the presentdisclosure.

FIG. 8 is a signaling flow diagram showing signaling for paging-based DLdata scheduling that occurs between a UE and base station when the UE isinitially in an RRC_CONNECTED state and when the UE is released andenters an RRC_INACTIVE state, according to aspects of the presentdisclosure.

FIG. 9 is a signaling flow diagram showing signaling for UL datatransmission in an INACTIVE UL BWP that occurs between a UE and basestation when the UE is initially in an RRC_CONNECTED state and when theUE is released and enters an RRC_INACTIVE state, according to furtheraspects of the present disclosure.

FIGS. 10 and 11 are flow diagrams illustrating methods according toaspects of the present disclosure.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

For illustrative purposes, specific example embodiments will now beexplained in greater detail below in conjunction with the figures.

The embodiments set forth herein represent information sufficient topractice the claimed subject matter and illustrate ways of practicingsuch subject matter. Upon reading the following description in light ofthe accompanying figures, those of skill in the art will understand theconcepts of the claimed subject matter and will recognize applicationsof these concepts not particularly addressed herein. It should beunderstood that these concepts and applications fall within the scope ofthe disclosure and the accompanying claims.

Moreover, it will be appreciated that any module, component, or devicedisclosed herein that executes instructions may include or otherwisehave access to a non-transitory computer/processor readable storagemedium or media for storage of information, such as computer/processorreadable instructions, data structures, program modules, and/or otherdata. A non-exhaustive list of examples of non-transitorycomputer/processor readable storage media includes magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,optical disks such as compact disc read-only memory (CD-ROM), digitalvideo discs or digital versatile discs (i.e. DVDs), Blu-ray Disc™, orother optical storage, volatile and non-volatile, removable andnon-removable media implemented in any method or technology,random-access memory (RAM), read-only memory (ROM), electricallyerasable programmable read-only memory (EEPROM), flash memory or othermemory technology. Any such non-transitory computer/processor storagemedia may be part of a device or accessible or connectable thereto.Computer/processor readable/executable instructions to implement anapplication or module described herein may be stored or otherwise heldby such non-transitory computer/processor readable storage media.

FIGS. 1, 2A, 2B and 3 illustrate examples of networks and devices thatcould implement any or all aspects of the present disclosure.

FIG. 1 illustrates an example communication system 100. In general, thesystem 100 enables multiple wireless or wired elements to communicatedata and other content. The purpose of the system 100 may be to providecontent (voice, data, video, text) via broadcast, narrowcast, userdevice to user device, etc. The system 100 may operate efficiently bysharing resources such as bandwidth.

In this example, the communication system 100 includes electronicdevices (ED) 110 a-110 c, radio access networks (RANs) 120 a-120 b, acore network 130, a public switched telephone network (PSTN) 140, theInternet 150, and other networks 160. Although certain numbers of thesecomponents or elements are shown in FIG. 1, any reasonable number ofthese components or elements may be included in the system 100.

The EDs 110 a-110 c are configured to operate, communicate, or both, inthe system 100. For example, the EDs 110 a-110 c are configured totransmit, receive, or both via wireless communication channels. Each ED110 a-110 c represents any suitable end user device for wirelessoperation and may include such devices (or may be referred to) as a userequipment/device (UE), wireless transmit/receive unit (WTRU), mobilestation, mobile subscriber unit, cellular telephone, station (STA),machine type communication device (MTC), personal digital assistant(PDA), smartphone, laptop, computer, touchpad, wireless sensor, orconsumer electronics device.

In FIG. 1, the RANs 120 a-120 b include base stations 170 a-170 b,respectively. Each base station 170 a-170 b is configured to wirelesslyinterface with one or more of the EDs 110 a-110 c to enable access toany other base station 170 a-170 b, the core network 130, the PSTN 140,the internet 150, and/or the other networks 160. For example, the basestations 170 a-170 b may include (or be) one or more of severalwell-known devices, such as a base transceiver station (BTS), a Node-B(NodeB), an evolved NodeB (eNodeB), a Home eNodeB, a gNodeB, atransmission and receive point (TRP), a site controller, an access point(AP), or a wireless router. Any ED 110 a-110 c may be alternatively oradditionally configured to interface, access, or communicate with anyother base station 170 a-170 b, the internet 150, the core network 130,the PSTN 140, the other networks 160, or any combination of thepreceding. The communication system 100 may include RANs, such as RAN120 b, wherein the corresponding base station 170 b accesses the corenetwork 130 via the internet 150, as shown.

The EDs 110 a-110 c and base stations 170 a-170 b are examples ofcommunication equipment that can be configured to implement some or allof the functionality and/or embodiments described herein. In theembodiment shown in FIG. 1, the base station 170 a forms part of the RAN120 a, which may include other base stations, base station controller(s)(BSC), radio network controller(s) (RNC), relay nodes, elements, and/ordevices. Any base station 170 a, 170 b may be a single element, asshown, or multiple elements, distributed in the corresponding RAN, orotherwise. Also, the base station 170 b forms part of the RAN 120 b,which may include other base stations, elements, and/or devices. Eachbase station 170 a-170 b transmits and/or receives wireless signalswithin a particular geographic region or area, sometimes referred to asa “cell” or “coverage area”. A cell may be further divided into cellsectors, and a base station 170 a-170 b may, for example, employmultiple transceivers to provide service to multiple sectors. In someembodiments, there may be established pico or femto cells where theradio access technology supports such. In some embodiments, multipletransceivers could be used for each cell, for example usingmultiple-input multiple-output (MIMO) technology. The number of RAN 120a-120 b shown is exemplary only. Any number of RAN may be contemplatedwhen devising the communication system 100.

The base stations 170 a-170 b communicate with one or more of the EDs110 a-110 c over one or more air interfaces 190 using wirelesscommunication links e.g. radio frequency (RF), microwave, infrared (IR),etc. The air interfaces 190 may utilize any suitable radio accesstechnology. For example, the communication system 100 may implement oneor more orthogonal or non-orthogonal channel access methods, such ascode division multiple access (CDMA), time division multiple access(TDMA), frequency division multiple access (FDMA), orthogonal FDMA(OFDMA), or single-carrier FDMA (SC-FDMA) in the air interfaces 190.

A base station 170 a-170 b may implement Universal MobileTelecommunication System (UMTS) Terrestrial Radio Access (UTRA) toestablish an air interface 190 using wideband CDMA (WCDMA). In doing so,the base station 170 a-170 b may implement protocols such as High SpeedPacket Access (HSPA), Evolved HPSA (HSPA+) optionally including HighSpeed Downlink Packet Access (HSDPA), High Speed Packet Uplink Access(HSUPA) or both. Alternatively, a base station 170 a-170 b may establishan air interface 190 with Evolved UTMS Terrestrial Radio Access (E-UTRA)using LTE, LTE-A, LTE-B and/or 5G New Radio (NR). It is contemplatedthat the communication system 100 may use multiple channel accessfunctionality, including such schemes as described above. Other radiotechnologies for implementing air interfaces include IEEE 802.11,802.15, 802.16, CDMA2000, CDMA2000 1×, CDMA2000 EV-DO, IS-2000, IS-95,IS-856, GSM, EDGE, and GERAN. Of course, other multiple access schemesand wireless protocols may be utilized.

The RANs 120 a-120 b are in communication with the core network 130 toprovide the EDs 110 a-110 c with various services such as voice, data,and other services. The RANs 120 a-120 b and/or the core network 130 maybe in direct or indirect communication with one or more other RANs (notshown), which may or may not be directly served by core network 130, andmay or may not employ the same radio access technology as RAN 120 a, RAN120 b or both. The core network 130 may also serve as a gateway accessbetween (i) the RANs 120 a-120 b or EDs 110 a-110 c or both, and (ii)other networks (such as the PSTN 140, the internet 150, and the othernetworks 160).

The EDs 110 a-110 c communicate with one another over one or more SL airinterfaces 180 using wireless communication links e.g. radio frequency(RF), microwave, infrared (IR), etc. The SL air interfaces 180 mayutilize any suitable radio access technology, and may be substantiallysimilar to the air interfaces 190 over which the EDs 110 a-110 ccommunication with one or more of the base stations 170 a-170 c, or theymay be substantially different. For example, the communication system100 may implement one or more channel access methods, such as codedivision multiple access (CDMA), time division multiple access (TDMA),frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), orsingle-carrier FDMA (SC-FDMA) in the SL air interfaces 180. In someembodiments, the SL air interfaces 180 may be, at least in part,implemented over unlicensed spectrum.

In this disclosure, the SL transmissions between cooperating UEs may be“grant-free” transmissions or as a mode for data transmissions that areperformed without communicating dynamic scheduling. Grant-freetransmissions are sometimes called “configured grant”, “grant-less”,“schedule free”, or “schedule-less” transmissions. Grant-free SLtransmissions can also be referred to as SL “transmission withoutgrant”, “transmission without dynamic grant”, “transmission withoutdynamic scheduling”, or “transmission using configured grant”, forexample.

A configured grant transmission typically requires the receiver to knowthe parameters and resources used by the transmitter for thetransmission. However, in the context of SL transmissions, the receivingUE is typically not aware of the transmitting UE's configurationparameters, such as which UE is transmitting, the ultimate target of thedata (e.g., another UE), the time-domain and frequency-domaincommunication resources used for the transmission, and other controlinformation. The various methods will, however, each incur a respectiveoverhead penalty.

In addition, some or all of the EDs 110 a-110 c may includefunctionality for communicating with different wireless networks overdifferent wireless links using different wireless technologies and/orprotocols. Instead of wireless communication (or in addition thereto),the EDs may communicate via wired communication channels to a serviceprovider or switch (not shown), and to the internet 150. PSTN 140 mayinclude circuit switched telephone networks for providing plain oldtelephone service (POTS). Internet 150 may include a network ofcomputers and subnets (intranets) or both, and incorporate protocols,such as internet protocol (IP), transmission control protocol (TCP) anduser datagram protocol (UDP). EDs 110 a-110 c may be multimode devicescapable of operation according to multiple radio access technologies,and incorporate multiple transceivers necessary to support multipleradio access technologies.

FIGS. 2A and 2B illustrate example devices that may implement themethods and teachings according to this disclosure. In particular, FIG.2A illustrates an example ED 110, and FIG. 2B illustrates an examplebase station 170. These components could be used in the system 100 or inany other suitable system.

As shown in FIG. 2A, the ED 110 includes at least one processor orprocessing unit 200. The processing unit 200 implements variousprocessing operations of the ED 110. For example, the processing unit200 could perform signal coding, bit scrambling, data processing, powercontrol, input/output processing, or any other functionality enablingthe ED 110 to operate in the communication system 100. The processingunit 200 may also be configured to implement some or all of thefunctionality and/or embodiments described in more detail herein. Eachprocessing unit 200 includes any suitable processing or computing deviceconfigured to perform one or more operations. Each processing unit 200could, for example, include a microprocessor, microcontroller, digitalsignal processor, field programmable gate array, or application specificintegrated circuit.

The ED 110 also includes at least one transceiver 202. The transceiver202 is configured to modulate data or other content for transmission byat least one antenna or Network Interface Controller (NIC) 204. Thetransceiver 202 is also configured to demodulate data or other contentreceived by the at least one antenna 204. Each transceiver 202 includesany suitable structure for generating signals for wireless or wiredtransmission and/or processing signals received wirelessly or by wire.Each antenna 204 includes any suitable structure for transmitting and/orreceiving wireless or wired signals. One or multiple transceivers 202could be used in the ED 110. One or multiple antennas 204 could be usedin the ED 110. Although shown as a single functional unit, a transceiver202 could also be implemented using at least one transmitter and atleast one separate receiver.

The ED 110 further includes one or more input/output devices 206 orinterfaces (such as a wired interface to the internet 150). Theinput/output devices 206 permit interaction with a user or other devicesin the network. Each input/output device 206 includes any suitablestructure for providing information to or receiving information from auser, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network interface communications.

In addition, the ED 110 includes at least one memory 208. The memory 208stores instructions and data used, generated, or collected by the ED110. For example, the memory 208 could store software instructions ormodules configured to implement some or all of the functionality and/orembodiments described above and that are executed by the processingunit(s) 200. Each memory 208 includes any suitable volatile and/ornon-volatile storage and retrieval device(s). Any suitable type ofmemory may be used, such as random access memory (RAM), read only memory(ROM), hard disk, optical disc, subscriber identity module (SIM) card,memory stick, secure digital (SD) memory card, and the like.

As shown in FIG. 2B, the base station 170 includes at least oneprocessing unit 250, at least one transmitter 252, at least one receiver254, one or more antennas 256, at least one memory 258, and one or moreinput/output devices or interfaces 266. A transceiver, not shown, may beused instead of the transmitter 252 and receiver 254. A scheduler 253may be coupled to the processing unit 250. The scheduler 253 may beincluded within or operated separately from the base station 170. Theprocessing unit 250 implements various processing operations of the basestation 170, such as signal coding, bit scrambling, data processing,power control, input/output processing, or any other functionality. Theprocessing unit 250 can also be configured to implement some or all ofthe functionality and/or embodiments described in more detail above.Each processing unit 250 includes any suitable processing or computingdevice configured to perform one or more operations. Each processingunit 250 could, for example, include a microprocessor, microcontroller,digital signal processor, field programmable gate array, or applicationspecific integrated circuit.

Each transmitter 252 includes any suitable structure for generatingsignals for wireless or wired transmission to one or more EDs or otherdevices. Each receiver 254 includes any suitable structure forprocessing signals received wirelessly or by wire from one or more EDsor other devices. Although shown as separate components, at least onetransmitter 252 and at least one receiver 254 could be combined into atransceiver. Each antenna 256 includes any suitable structure fortransmitting and/or receiving wireless or wired signals. Although acommon antenna 256 is shown here as being coupled to both thetransmitter 252 and the receiver 254, one or more antennas 256 could becoupled to the transmitter(s) 252, and one or more separate antennas 256could be coupled to the receiver(s) 254. Each memory 258 includes anysuitable volatile and/or non-volatile storage and retrieval device(s)such as those described above in connection to the ED 110. The memory258 stores instructions and data used, generated, or collected by thebase station 170. For example, the memory 258 could store softwareinstructions or modules configured to implement some or all of thefunctionality and/or embodiments described above and that are executedby the processing unit(s) 250.

Each input/output device 266 permits interaction with a user or otherdevices in the network. Each input/output device 266 includes anysuitable structure for providing information to or receiving/providinginformation from a user, including network interface communications.

Additional details regarding the UEs 110 and the base stations 170 areknown to those of skill in the art. As such, these details are omittedhere for clarity.

FIG. 3 illustrates a schematic diagram of an air interface manager 300for configuring a software-configurable air interface 190. The airinterface manager 300 may be, for example, a module including a numberof components or building blocks that define the parameters of the airinterface 190 and collectively specify how a transmission is to be madeand/or received by the air interface 190. The air interface manger 300could also or instead define the parameters of the SL air interface 180and collectively specify how a transmission is to be made and/orreceived by the SL air interface 180

The components of the air interface manger 300 include at least one of awaveform component 305, a frame structure component 310, a multipleaccess scheme component 315, a protocol component 320, and a modulationand coding component 325.

The waveform component 305 may specify a shape and form of a signalbeing transmitted. Waveform options may include orthogonal multipleaccess waveforms and non-orthogonal multiple access waveforms.Non-limiting examples of such waveform options include Single-Carrier(SC), Ultra-Wideband (UWB), Frequency Modulated Continuous Wave (FMCW),Linear Frequency Modulated (LFM), Orthogonal Frequency DivisionMultiplexing (OFDM), Single-Carrier Frequency Division Multiple Access(SC-FDMA), Filtered OFDM (f-OFDM), Time windowing OFDM, Filter BankMulticarrier (FBMC), Universal Filtered Multicarrier (UFMC), GeneralizedFrequency Division Multiplexing (GFDM), Wavelet Packet Modulation (WPM),Faster Than Nyquist (FTN) Waveform, and low Peak to Average Power RatioWaveform (low PAPR WF). In some embodiments, a combination of waveformoptions is possible.

The frame structure component 310 may specify a configuration of a frameor group of frames. The frame structure component 310 may indicate oneor more of a time, frequency, pilot signature, code, or other parameterof the frame or group of frames.

Non-limiting examples of frame structure options include: the number ofsymbols in the time slot, the number of time slots in the frame and theduration of each time slot (sometimes known as a transmission timeinterval, TTI, or a transmission time unit, TTU). The frame structurecomponent may also specify whether the time slot is a configurablemulti-level TTI, a fixed TTI, or a configurable single-level TTI. Theframe structure component may further specify a co-existence mechanismfor different frame structure configurations.

For some waveforms, such as certain OFDM-based waveforms, the framestructure component may also specify one or more associated waveformparameters, such as sub-carrier spacing width, symbol duration, cyclicprefix (CP) length, channel bandwidth, guard bands/subcarriers, andsampling size and frequency.

Additionally, the frame structure component 310 may further specifywhether the frame structure is used in a time-division duplexcommunication or a frequency-division duplex communication.

Additionally, the frame structure component 310 may further specify thetransmission state and/or direction for each symbol in a frame. Forexample, each symbol may independently be configured as a downlinksymbol, an uplink symbol, or a flexible symbol.

Together, the specifications of the waveform component and the framestructure component are sometimes known as the “numerology.” Thus, theair interface 190 may include a numerology component 330 defining anumber of air interface configuration parameters, such as thesub-carrier spacing, CP length, symbol length, slot length, and symbolsper slot.

These numerologies, also known as subcarrier spacing configurations, maybe scalable in the sense that subcarrier spacings of differentnumerologies are multiples of each other, and time slot lengths ofdifferent numerologies are also multiples of each other. Such a scalabledesign across multiple numerologies provides implementation benefits,for example scalable total OFDM symbol duration in a time divisionduplex (TDD) context.

Frames can be configured using one or a combination of scalablenumerologies. For example, a numerology with 60 kHz subcarrier spacinghas a relatively short OFDM symbol duration (because OFDM symbolduration varies inversely with subcarrier spacing), which makes the 60kHz numerology particularly suitable for ultra-low latencycommunications, such as Vehicle-to-Any (V2X) communications. A furtherexample of a numerology with a relatively short OFDM symbol durationsuitable for low latency communications is a numerology with 30 kHzsubcarrier spacing. A numerology with 15 kHz subcarrier spacing may becompatible with LTE. A numerology with 15 kHz subcarrier spacing mayserve as a default numerology for initial access of a device to anetwork. This 15 kHz numerology may also be suitable for broadbandservices. A numerology with 7.5 kHz spacing, which has a relatively longOFDM symbol duration, may be particularly useful for coverageenhancement and broadcasting. Additional uses for these numerologieswill be or become apparent to persons of ordinary skill in the art. Ofthe four numerologies listed, those with 30 kHz and 60 kHz subcarrierspacings are more robust to Doppler spreading (fast moving conditions),because of the wider subcarrier spacing. It is further contemplated thatdifferent numerologies may use different values for other physical layerparameters, such as the same subcarrier spacing and different cyclicprefix lengths. In addition, subcarrier spacing may depend on theoperational frequency band. For example, the subcarrier spacing inmillimeter wave frequencies may be higher than in lower frequencies.

It is further contemplated that other subcarrier spacings may be used,such as higher or lower subcarrier spacings. For example, othersubcarrier spacings varying by a factor of 2^(n) include 120 kHz and3.75 kHz.

In other examples, a more limited scalability may be implemented, inwhich two or more numerologies all have subcarrier spacings that areinteger multiples of the smallest subcarrier spacing, withoutnecessarily being related by a factor of 2^(n). Examples include 15 kHz,30 kHz, 45 kHz, 60 kHz subcarrier spacings.

In still other examples, non-scalable subcarrier spacings may be used,which are not all integer multiples of the smallest subcarrier spacing,such as 15 kHz, 20 kHz, 30 kHz, 60 kHz.

OFDM-based signals can be employed to transmit a signal in whichmultiple numerologies coexist simultaneously. More specifically,multiple sub-band OFDM signals can be generated in parallel, each withina different sub-band, and each sub-band having a different subcarrierspacing (and more generally with a different numerology). The multiplesub-band signals are combined into a single signal for transmission, forexample for downlink transmissions. Alternatively, the multiple sub-bandsignals may be transmitted from separate transmitters, for example foruplink transmissions from multiple electronic devices (EDs), which maybe user equipments (UEs).

The use of different numerologies can allow the air interface 190 tosupport coexistence of a diverse set of use cases having a wide range ofquality of service (QoS) requirements, such as different levels oflatency or reliability tolerance, as well as different bandwidth orsignaling overhead requirements. In one example, the base station cansignal to the ED an index representing a selected numerology, or asingle parameter (e.g., subcarrier spacing) of the selected numerology.Based on this signaling, the ED may determine the parameters of theselected numerology from other information, such as a look-up table ofcandidate numerologies stored in memory.

Continuing with the components of the air interface 190, the multipleaccess scheme component 315 may specify how access to a channel isgranted for one or more EDs. Non-limiting examples of multiple accesstechnique options include technologies defining how EDs share a commonphysical channel, such as: Time Division Multiple Access (TDMA),Frequency Division Multiple Access (FDMA), Code Division Multiple Access(CDMA), Space Division Multiple Access (SDMA), Single Carrier FrequencyDivision Multiple Access (SC-FDMA), Low Density Signature MulticarrierCode Division Multiple Access (LDS-MC-CDMA), Non-Orthogonal MultipleAccess (NOMA), Pattern Division Multiple Access (PDMA), LatticePartition Multiple Access (LPMA), Resource Spread Multiple Access(RSMA), and Sparse Code Multiple Access (SCMA). Furthermore, themultiple access technique options may include scheduled access,non-scheduled access, also known as grant-free access or configuredgrant, contention-based shared channel resource, non-contention-basedshared channel resource, and cognitive radio-based access.

The protocol component 320 may specify how a transmission and/or are-transmission are to be made. Non-limiting examples of transmissionand/or re-transmission mechanism options include those that specify ascheduled data pipe size and a signaling mechanism for transmissionand/or re-transmission.

The modulation and coding component 325 may specify how informationbeing transmitted may be encoded/decoded and modulated/demodulated fortransmission/reception purposes. Coding may refer to methods of errordetection and forward error correction. Non-limiting examples of codingoptions include turbo trellis codes, turbo product codes, fountaincodes, low-density parity check codes, and polar codes. Modulation mayrefer, simply, to Quadrature Amplitude Modulation (QAM) specified by acomplex constellation (including, for example, the modulation techniqueand order, e.g. 16QAM, 64QAM, etc.), or more specifically to varioustypes of advanced modulation methods such as hierarchical modulation,multi-dimensional modulation and low Peak-to-Average Power Ratio (PAPR)modulation.

Because an air interface includes a plurality of components or buildingblocks, and each component may have a plurality of candidatetechnologies (also referred to herein as air interface capabilityoptions), the air interface manager 300 may configure and store a largenumber of different air interface profiles. Each air interface profiledefines a respective set of air interface capability options.

For example, in each air interface profile defining a respective set ofair interface capability options, an air interface capability option isselected for each of the component building blocks of the air interface.Each of the different air interface profiles may be targeted to meet adifferent set of transmission requirements, including transmissioncontent, transmit condition, and receive condition.

According to the transmission requirements of a pair of communicatingtransmitting-receiving devices, one of the different air interfaceprofiles that best meet the transmission requirements may be selectedfrom the air interface manager 300 and used for communications betweenthe pair of communicating transmitting-receiving devices.

In further embodiments, the air interface manager 300 may modify orupdate its components, profiles, or capability options. For example, theair interface manager 300 may replace the waveform and frame structurecomponents 305, 310, with a single numerology component 330. Conversely,the air interface manager 300 may separate the modulation and codingcomponent 325 into an individual coding component and an individualmodulation component. Furthermore, the air interface manager 300 isconfigurable such that new soft air interface configuration componentsdeveloped in the future should be able to be utilized.

The air interface manager 300 may also update certain components tomodify the capability options of any given component. For example, theair interface manager 300 may update the modulation and coding component325 to include higher-order modulation schemes.

By updating the stored components, profiles, and candidate options, theair interface manager 300 can flexibly adapt to better accommodatediverse wireless traffic types and services. Modifying or updatingcomponents, profiles, and candidate options may allow the air interfacemanager 300 to provide suitable air interface profiles for traffic typesor services other than those already contemplated for ultra-reliable lowlatency communications (URLLC), enhanced mobile broadband (eMBB), andmassive machine-type communications (mMTC).

As noted above, in 3GPP New Radio (NR), a UE may operate in one of thefollowing three states: RRC_IDLE, RRC_CONNECTED and RRC_INACTIVE.

The RRC_CONNECTED state is a non-limiting example of a connected oractive state. A UE in the RRC_CONNECTED state is connected to the radioaccess network (RAN) and to the core network (CN). The UE could enterthe RRC_CONNECTED state from the RRC_IDLE state following a connectionestablishment procedure or from the RRC_INACTIVE state following aconnection resumption procedure, for example. The RRC_CONNECTED statecan be characterized as including the following features:

-   -   the UE stores the access stratum (AS) context;    -   a transfer of unicast data to and from the UE is supported;    -   at lower layers, the UE may be configured with UE-specific        discontinuous reception (DRX);    -   for UEs supporting carrier aggregation (CA), use of one or more        secondary cells (SCells), aggregated with a special cell        (SpCell), is supported for increased bandwidth;    -   for UEs supporting dual connectivity (DC), use of a secondary        cell group (SCG), aggregated with the master cell group (MCG),        is supported for increased bandwidth;    -   network controlled mobility is supported within a NR network and        to/from an E-UTRA network;    -   the UE monitors short messages transmitted with a paging radio        network temporary identifier (P-RNTI) over downlink control        information (DCI), if configured;    -   the UE monitors control channels associated with the shared data        channel to determine if data is scheduled for the UE;    -   the UE provides channel quality and feedback information to the        network;    -   the UE performs neighboring cell measurements and measurement        reporting; and    -   the UE acquires system information.

The RRC_IDLE state is a non-limiting example of an idle or disconnectedstate. A UE in the RRC_IDLE state is not connected to the RAN or the CN,and the UE may need to perform an initial access procedure to establisha connection to the network and transition to the RRC_CONNECTED state.The RRC_IDLE state can be characterized as including the followingfeatures:

-   -   UE-specific DRX may be configured by upper layers of the        network;    -   UE controlled mobility is based on network configuration;    -   the UE monitors short messages transmitted with the P-RNTI over        DCI;    -   the UE monitors a paging channel for CN paging using a 5G system        architecture evolution temporary mobile station identifier        (5G-S-TMSI);    -   the UE performs neighboring cell measurements and cell selection        or cell reselection; and    -   the UE acquires system information (SI) and can send a SI        request, if configured.

The RRC_INACTIVE state is a non-limiting example of an inactive state. AUE in an inactive state uses fewer network resources and/or less powerthan a UE in a connected state. This may save battery life at the UE.When a UE transitions to the inactive state, configuration informationfor the UE is stored by the UE and the network. This allows the UE toreturn to the connected state relatively quickly and efficiently. Forexample, a UE may use less signaling to transition from an inactivestate to a connected state than from an idle state to a connected state.

The RRC_INACTIVE state could be considered to lie between theRRC_CONNECTED and RRC_IDLE states. In the RRC_INACTIVE state, at least aportion of the UE's AS context is stored by both the UE and the network,which allows the network to communicate with the UE. Therefore, secureand fast signaling could occur between the network and the UE. Moreover,a UE in the RRC_IDLE state might only support CN paging that isperformed in the tracking area where the UE is located. In contrast, aUE in the RRC_INACTIVE state may, in addition to CN paging, also supportRAN paging that is performed in the RAN notification area (RNA) wherethe UE is located. Because a RNA typically covers a smaller number ofcells than a tracking area, RAN paging in the RRC_INACTIVE state mayincur less DL resource consumption and/or overhead. The RRC_INACTIVEstate can be characterized as including the following features:

-   -   UE-specific DRX may be configured by upper layers of the network        or by the RRC layer;    -   UE controlled mobility is based on network configuration;    -   the UE stores an inactive AS context, which could be different        from the AS context used in the RRC_CONNECTED state;    -   a RAN-based notification area is configured by the RRC layer;    -   the UE monitors short messages transmitted with P-RNTI over DCI;    -   the UE monitors a paging channel for CN paging using 5G-S-TMSI        and RAN paging using a FulII-RNTI;    -   the UE performs neighboring cell measurements and cell selection        or cell reselection;    -   the UE performs RAN-based notification area updates periodically        and when moving outside the configured RAN-based notification        area; and    -   the UE acquires SI and can send an SI request, if configured.

The RRC_INACTIVE state is implemented in NR, but in general an inactivestate could be implemented in any wireless protocol or radio technology.Accordingly, inactive states are not limited to a particular wirelessprotocol or radio technology. Similar comments apply to idle states andconnected states.

A UE can transition from a connected state to an inactive state using asuspend procedure, and transition back to the connected state using aresume procedure. The UE can also transition from the inactive state tothe idle state using a release procedure. The transition from theconnected state to the inactive state is invisible to the CN. Therefore,when a UE is in the inactive state, UE-related signaling and dataexchange can occur between the RAN and the CN. From the perspective ofthe CN, a UE in the inactive state is treated in a similar manner to aUE in the connected state. For example, from the perspective of the CN,a UE may have two connection management (CM) states. The UE is either ina CM-CONNECTED state or a CM-IDLE state. A UE in the CM-IDLE state inthe CN is in the RRC_IDLE state from the RAN point of view, whereas a UEin the CM-CONNECTED state in the CN may be either in the RRC_CONNECTEDstate or the RRC_INACTIVE state from the RAN point of view. The UE'ssecurity context and/or other portions of the UE's context is/are storedby the UE and by the network before the UE transitions from theconnected state to the inactive state. Thus, the network can quickly andsecurely transmit signaling to the UE for a transition from the inactivestate to the connected or idle states.

In NR Rel-15, when a UE is in the RRC_INACTIVE state or the RRC_IDLEstate, the UE monitors a Paging Common Search Space (CSS) set andreceives a paging signal on physical downlink shared channel (PDSCH) incontrol resource set (CORESET) with ID 0, which is often referred to asCORESET 0. A CORESET is a set of physical resources, e.g. a set ofresource blocks (RBs) and a number of symbols, over which a physicaldownlink control channel (PDCCH) may be transmitted and a set of otherphysical parameters that may be used to transmit PDCCH. A PDCCH mayinclude downlink control information (DCI). A search space set providesall the parameters needed for a UE to be able to monitor a PDCCH.CORESETs may be separately configured and linked to a search space setas part of the search space set configuration. Alternatively, CORESETparameters may be configured directly as part of a search space setconfiguration. The parameters provided in a search space setconfiguration, in addition to CORESET parameters, may include, but arenot limited to: a PDCCH monitoring periodicity, a PDCCH monitoringpattern within a slot, a number of slots where the search space setexists, control channel element (CCE) aggregation level(s), a number ofPDCCH candidates for each aggregation level, a type of the search spaceset, e.g. either common search space (CSS) or UE-specific search space(USS), and DCI format(s) to be monitored in the search space set.

In NR Rel-15, a bandwidth part (BWP) is a set of contiguous resourceblocks (RBs) with a given numerology on a given carrier. The set ofcontiguous RBs of a BWP is identified by its frequency location andbandwidth. A BWP can be a DL BWP, which is used for DL communicationsbetween a UE and a base station, or an UL BWP, which is used for ULcommunications between the UE and the base station. A UE-specific DL orUL BWP is configured to the UE using UE-specific higher layer signaling.In NR Rel-15, a UE can be configured with more than one DL BWP and morethan one UL BWP, with a single DL BWP and a single UL BWP being activefor the UE at a given time. A DL BWP can be cell-specific, such as theDL BWP defined by the contiguous RBs of CORESET 0, which can beconfigured per cell e.g. through master information block (MIB)transmission. An UL BWP can also be cell-specific, such as the initialUL BWP which can be configured per cell e.g. through system informationblock (SIB) transmission.

For uplink (UL), a 4-step RACH or possibly a 2-step RACH may besupported for a UE in the RRC_INACTIVE state, in which an ULtransmission is transmitted in the initial UL BWP.

CORESET 0 is intended to be used by all UEs for DL communication atleast during initial access to the cell and possibly for many UEsconnected to the cell after the initial access to the cell. BecauseCORESET 0 may span only a portion of the carrier bandwidth in DL,restriction of using CORESET 0 for DL communication, e.g. DL data and DLcontrol transmissions, in the RRC_INACTIVE state may overload thebandwidth of CORESET 0, because there are potentially many UEs withsmall packet traffic in the RRC_INACTIVE state.

Initial UL BWP is intended to be used by all UEs for UL communication atleast during initial access to the cell and possibly for many UEsconnected to the cell after the initial access to the cell. Because theinitial UL BWP may span only a portion of the carrier bandwidth in UL,the restriction of using the initial UL BWP for UL communication, e.g.UL data and/or UL control and/or UL reference signal transmissions, inthe RRC_INACTIVE state may overload the bandwidth of the initial UL BWP,because there are potentially many UEs with small packet traffic in theRRC_INACTIVE state.

In the present disclosure, mechanisms are proposed for configuration ofresources (frequency and time) for transmission in the RRC_INACTIVEstate, so that more efficient and flexible resource management may beachieved.

The air interface parameters currently supported in NR, e.g. cyclicprefix (CP) lengths, may not provide an acceptable support of UL timingadjust (TA)—free transmissions for a UE in the RRC_INACTIVE state.

Some aspects of the present disclosure introduce a new DL BWP, calledINACTIVE DL BWP, for DL communication in RRC_INACTIVE state. A new ULBWP, called INACTIVE UL BWP, for UL communication in RRC_INACTIVE stateis also introduced. In addition, aspects of the disclosure also providefor configuring the generic parameters of the INACTIVE DL BWP orINACTIVE UL BWP, which include, but not limited to, frequency location,bandwidth, subcarrier spacing (SCS), and CP.

The INACTIVE DL BWP or INACTIVE UL BWP can be specific to particular UEsbeing served by a base station (UE-specific), specific to particulargroup of UEs being served by a base station (group-common), or appliedto all UE being served by a base station (cell-specific BWP).

A result of the above configuration is that every UE-specific DLreception or UL transmission in the RRC_INACTIVE state occurs within theINACTIVE DL (UL) BWP.

In some embodiments, such a configuration may result in new BWPconfiguration parameters.

A benefit of the INACTIVE DL BWP or INACTIVE UL BWP for the RRC_INACTIVEstate may be efficient resource management for data transmission in theRRC_INACTIVE state, for example because the network may not berestricted to use only CORETSET 0 for DL communication with UEs inRRC_INACTIVE state or to use only the initial UL BWP for ULcommunication with UEs in RRC_INACTIVE state.

Some aspects of the present disclosure may support a reinterpretation ofconfigured parameters of a BWP, for example generic parameters of a BWP,which may be configured for the RRC_CONNECTED state, to be used in theRRC_INACTIVE state.

This reinterpretation of BWPs configured for another state, such as theRRC_CONNECTED state, to be used in the RRC_INACTIVE state, can bespecific to particular UEs being served by a base station (UE-specific)or specific to particular group of UEs being served by a base station(group-common), or applied to all UE being served by a base station(cell-specific BWP).

Some embodiments of the above configuration mechanism result in new UEbehaviors with respect to some existing BWP configuration parameters.

Some embodiments of the above configuration mechanism result in definingnew CP lengths for UL.

Being able to reinterpret parameter information for the RRC_INACTIVEstate based on parameter information from another state may bebeneficial, because the reinterpretation may not necessitate anysignificant changes to radio resource control mechanisms currently beingused. Another benefit of this approach may be that it supports longerCPs for UL TA-free transmission in RRC_INACTIVE state.

Some aspects of the present disclosure are directed to implicit DL BWPswitching in the RRC_INACTIVE state where no BWP identifier (ID)indication is needed as part of the switching mechanism.

Some embodiments pertain to defining conditions for DL BWP switching inthe RRC_INACTIVE state. Some embodiments pertain to implicit DL BWPswitching before receiving unicast or multicast PDSCH. Some embodimentspertain to autonomous DL BWP switching after receiving unicast ormulticast PDSCH.

Some embodiments pertain to defining conditions for UL BWP switching inthe RRC_INACTIVE state. Some embodiments pertain to implicit UL BWPswitching before transmitting PUSCH. Some embodiments pertain toautonomous UL BWP switching after transmitting PUSCH.

Some embodiments of the above configuration mechanism result in definingnew UE behaviors with respect to DCI based DL scheduling or Paging basedDL scheduling, or both.

Some embodiments of the above configuration mechanism result in definingnew BWP switching delay for the RRC_INACTIVE state.

Aspects of controlling switching of DL BWPs in the RRC_INACTIVE statemay result in efficient resource management for data transmission in theRRC_INACTIVE state, power savings at the UE by adjusting the radiofrequency bandwidth (RF BW) and support of different numerologies forpaging and transmission of unicast DL data.

Embodiment 1-0

Some aspects of the present application relate to configuration ofgeneric parameters of BWP for the RRC_INACTIVE state. The RRC_INACTIVEstate may also be referred to as the INACTIVE BWP state.

Some embodiments of the disclosure provide a configuration for aUE-specific DL BWP or UE-specific UL BWP. Some embodiments of thedisclosure provide a configuration for a group-common DL BWP orgroup-common UL BWP.

In some embodiments, the configuration is an explicit configuration ofthe BWP parameters. For example the DL or UL BWP is explicitlyconfigured in ServingCellConfig parameter or in an RRCRelease messagesent as part of a suspension of the active RRC connection.

In some embodiments, the DL or UP BWP may be configured implicitly.

In a first example of a configuration implemented implicitly, a DL or ULBWP is configured by indicating a BWP-Id. The BWP-Id identifies a DL orUL BWP that has been previously configured in a ServingCellConfigparameter or in an RRCRelease for suspension of the connection. In someembodiments, this may be implemented by pointing to one of the DL or ULBWPs in a downlinkBWP-ToAddModList parameter or anuplinkBWP-ToAddModList parameter.

In a second example, a DL BWP used for the RRC_INACTIVE state is basedon the active DL BWP used by the UE in which the UE receives thephysical downlink shared channel (PDSCH) containing an RRCReleasemessage in the RRC_CONNECTED state that suspends the RRC connection.

In a third example, a DL BWP used for the RRC_INACTIVE state is based onthe last active DL BWP of the UE before transitioning to theRRC_INACTIVE state.

FIGS. 4A to 4D illustrate four different examples of the configuredINACTIVE DL BWP following a transition from the RRC_CONNECTED state toRRC_INACTIVE state. In each of the figures the horizontal axiscorresponds to time, increasing from left to right and the vertical axiscorresponds to frequency. The various blocks shown in the figuresrepresent frequency resources of BWPs.

In FIG. 4A, two BWPs are shown in the portion of time indicated to be inthe RRC_CONNECTED state. A first BWP is CORESET 0 410, or moreparticularly, the set of contiguous RBs of CORESET 0 410. A second BWPis a last active DL BWP 420. The two BWPs occupy separate sets of RBs.After a UE transitions from the RRC_CONNECTED state to the RRC_INACTIVEstate a single DL BWP is used by the UE which is identified as theINACTIVE DL BWP 430. In this instance, the INACTIVE DL BWP 430 occupiesa same set of RBs as the last active DL BWP 420, which does not overlapwith the set of RBs occupied by CORESET 0 410.

In FIG. 4B, CORESET 0 410 and a last active DL BWP 420 are shown in theportion of time indicated to be in the RRC_CONNECTED state. The two BWPspartially overlap in frequency. After a UE transitions from theRRC_CONNECTED state to the RRC_INACTIVE state, the INACTIVE DL BWP 430is shown to occupy a same set of RBs as the last active DL BWP 420,which has some overlap with the set of RBs occupied by CORESET 0 410.

In FIG. 4C, CORESET 0 410 and a last active DL BWP 420 are shown in theportion of time indicated to be in the RRC_CONNECTED state. The lastactive DL BWP 420 includes an entire set of RBs of CORESET 0 410. Aftera UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state,the INACTIVE DL BWP 430 is shown to occupy a same set of RBs as the lastactive DL BWP 420, which totally overlaps with the set of RBs occupiedby CORESET 0 410.

In FIG. 4D, CORESET 0 410 and a last active DL BWP 420 are shown in theportion of time indicated to be in the RRC_CONNECTED state. The lastactive DL BWP 420 falls totally within a set of RBs of CORESET 0 410.After a UE transitions from the RRC_CONNECTED state to the RRC_INACTIVEstate, the INACTIVE DL BWP 430 is shown to occupy a same set of RBs asthe last active DL BWP 420, which is within the set of RBs occupied byCORESET 0 410.

In a fourth example, an UL BWP used for the RRC_INACTIVE state is basedon the last active UL BWP of the UE before transitioning to theRRC_INACTIVE state.

Some embodiments of the disclosure provide a configuration for aCell-specific INACTIVE DL BWP or Cell-specific INACTIVE UL BWP for theRRC_INACTIVE state.

In a first example, CORESET 0, i.e. a set of contiguous RBs, startingfrom an RB with the lowest index and ending at an RB with the highestindex among RBs of CORESET 0 is configured as a Cell-specific INACTIVEDL BWP. In a further example, a set of contiguous RBs of a CORESET forType0-PDCCH CSS set can be configured as a Cell-specific INACTIVE DLBWP.

In a second example, the initial DL or UL BWP used by the UE when the UEis in the RRC_CONNECTED state is used as a Cell-specific INACTIVE DL orUL BWP in the RRC_INACTIVE state.

In a third example, the INACTIVE DL or UL BWP for the RRC_INACTIVE stateis configured in system information block (SIB1), i.e. inservingCellConfigCommonSIB. For example, the INACTIVE DL or UL BWP forthe RRC_INACTIVE state in the RRC information elementDownlinkConfigCommonSIB or UplinkConfigCommonSIB inservingCellConfigCommonSIB.

In a fourth example, the INACTIVE DL or UL BWP for the RRC_INACTIVEstate is configured in a new system information block (SIBx) which isparticularly used for configurations related to data transmission inRRC_INACTIVE, where x≠1 is an integer.

Embodiment 1-1

In some embodiments, further restrictions may be placed on the locationand bandwidth of INACTIVE BWP. Such further restrictions may limitflexibility so as to avoid RF retuning by a UE in the RRC_INACTIVEstate.

In some embodiments, an INACTIVE DL BWP includes all RBs of CORESET 0.FIG. 4C is also a representative example of this particular situation.

In some embodiments, an INACTIVE UL BWP includes all RBs of the initialUL BWP.

Embodiment 1-2

In some embodiments, further restrictions may be placed on sub-carrierspacing (SCS) and cyclic prefix (CP) parameters of the INACTIVE BWP. Apossible benefit of these embodiments is to avoid a numerology change bya UE in the RRC_INACTIVE state, and thus, limit the complexity ofoperation of the UE and/or UE implementation in RRC_INACTIVE state.

In some embodiments, an INACTIVE DL BWP has a same SCS and a same CP asCORESET 0. In an example, i.e. an INACTIVE DL BWP has the same SCS andCP as a SCS and a CP for physical downlink control channel (PDCCH)reception in the CORESET for Type0-PDCCH CSS set.

In some embodiments, an INACTIVE UL BWP has a same SCS and a same CP asthe initial UL BWP.

Embodiment 2-1

Some embodiments of the present disclosure provide a reinterpretation ofgeneric BWP parameters for application to BWP to be used in theRRC_INACTIVE state.

One particular example is reinterpretation of CP length. A particularuse for reinterpretation of the CP length may be for an UL BWP in theRRC_INACTIVE state.

In some embodiments, when an extended CP length is indicated in a BWPconfiguration, the following interpretation may be used by the UE. Anormal CP with that SCS is used for the BWP when the UE is in theRRC_CONNECTED state and an extended CP with that SCS is used for the BWPwhen the UE is in the RRC_INACTIVE state. In an example, the mentionedinterpretation may only be applicable when the SCS is not 60 kHz.

In some embodiments, an extended CP length is always used with theconfigured SCS in the RRC_INACTIVE state, regardless of the CP lengthconfiguration of the SCS in the RRC_CONNECTED state.

The above described embodiments pertaining to CP length may beapplicable to any of the BWP configuration alternatives in Embodiments1-0, 1-1 and 1-2

In some embodiments, new extended CP values are defined for various SCS.In some embodiments, the extended CP values may be used for SCS whereextended CP values have not been previously defined, i.e. other than 60kHz. A particular example may be that an extended CP is indicated in theconfiguration of the initial UL BWP. For example, an extended CP for aparticular SCS is determined such that a number of OFDM symbols per slotof the SCS with the extended CP is equal to 12, whereas a number of OFDMsymbols per slot of the SCS with a normal CP is equal to 14. Aparticular example of the extended CP for the SCS is a CP length whichis equal to 25% of an OFDM symbol duration corresponding to the SCS,with the OFDM symbol duration being equal to a reciprocal of the SCSvalue.

Embodiment 2-2

Another particular example of reinterpretation of a generic parameter isreinterpretation of bandwidth and location of a BWP. There is somewhatlimited flexibility of reinterpreting these parameters so as to avoid RFretuning by a UE in the RRC_INACTIVE state.

In some embodiments, in the case of a UE-specific INACTIVE DL BWP, ifthe UE-specific INACTIVE DL BWP does not include all RBs of CORESET 0,the DL BWP to be used in the RRC_INACTIVE state can be defined by theRBs spanned by the UE-specific INACTIVE DL BWP and CORESET 0.

FIGS. 5A to 5C and FIG. 4C illustrate four different examples of theconfigured INACTIVE DL BWP following a transition from the RRC_CONNECTEDstate to RRC_INACTIVE state. In each of the figures the horizontal axiscorresponds to time, increasing form left to right and the vertical axiscorresponds to frequency. The various blocks shown in the figuresrepresent frequency resources of different BWPs.

In FIG. 5A, two transmission resources are shown in the portion of timeindicated to be in the RRC_CONNECTED state. A first BWP is CORESET 0510, or more particularly, a set of contiguous RBs of CORESET 0 510. Asecond BWP is a last active DL BWP 520. The two BWPs occupy separatesets of RBs. After a UE transitions from the RRC_CONNECTED state to theRRC_INACTIVE state a single BWP is used by the UE which is identified asthe INACTIVE DL BWP 530. In this instance, the INACTIVE DL BWP 530occupies a set of RBs that encompasses a set of RBs of the last activeDL BWP 520, occupies the set of RBs of CORESET 0 510 and the RBsseparating the two BWPs 510 and 520.

In FIG. 5B, CORESET 0 510 and a last active DL BWP 520 are shown in theportion of time indicated to be in the RRC_CONNECTED state. The BWPs 510and 520 partially overlap in frequency. After a UE transitions from theRRC_CONNECTED state to the RRC_INACTIVE state, the INACTIVE DL BWP 530is shown to occupy a set of RBs that encompasses the last active DL BWP520 and the RBs of CORESET 0 510.

In FIG. 5C, CORESET 0 510 and a last active DL BWP 520 are shown in theportion of time indicated to be in the RRC_CONNECTED state. A set of RBsof the last active DL BWP 520 falls totally within a set of RBs ofCORESET 0 510. After a UE transitions from the RRC_CONNECTED state tothe RRC_INACTIVE state, the INACTIVE DL BWP 530 is shown to occupy a setof RBs that encompasses CORESET 0 510, which also encompasses the set ofRBs of the last active DL BWP 520.

Referring again to FIG. 4C, CORESET 0 410 and the last active DL BWP 420are shown in the portion of time indicated to be in the RRC_CONNECTEDstate. The last active DL BWP 420 occupies the entire set of RBs ofCORESET 0 410. After a UE transitions from the RRC_CONNECTED state tothe RRC_INACTIVE state, the INACTIVE DL BWP 430 is shown to occupy a setof RBs that encompasses the last active DL BWP 420, which alsoencompasses the RBs of CORESET 0 410.

In some embodiments, in the case of a UE-specific INACTIVE UL BWP, ifthe UE-specific INACTIVE UL BWP does not include all resource blocks ofthe initial UL BWP, the UL BWP to be used in the RRC_INACTIVE state canbe defined by the RBs spanned by the UE-specific INACTIVE UL BWP and theinitial UL BWP.

Some aspects of the present disclosure pertain to implicit DL BWPswitching in RRC_INACTIVE state. In some embodiments, there is no BWP IDindication in the scheduling command for such switching.

Embodiment 3-1

In some embodiments, DL BWP switching is always assumed for DLunicast/multicast transmission in the RRC_INACTIVE state.

In some embodiments, DL BWP switching is assumed for DLunicast/multicast transmission in the RRC_INACTIVE state only when acondition is met. Several examples of the DL BWP switching condition,which are intended to be non-limiting, are included below.

In a first condition, the INACTIVE DL BWP has a different frequencylocation and bandwidth or a different SCS or a different CP length thanthe CORESET 0.

In a second condition, the INACTIVE DL BWP does not include all RBs ofCORESET 0 or, has a different SCS or a different CP than CORESET 0.

In some embodiments, UL BWP switching is always assumed for ULtransmission in the RRC_INACTIVE state.

In some embodiments, UL BWP switching is assumed for UL transmission inthe RRC_INACTIVE state only when a condition is met. Several examples ofthe UL BWP switching condition, which are intended to be non-limiting,are included below.

In a first condition, the INACTIVE UL BWP has a different frequencylocation and bandwidth or a different SCS or a different CP length thanthe initial UL BWP.

In a second condition, the INACTIVE UL BWP does not include all RBs ofthe initial UL BWP or, has a different SCS or a different CP than theinitial UL BWP.

FIG. 6A illustrates an example of when a condition for DL BWP switchingis met in the RRC_INACTIVE state, for example with respect to the secondcondition. In FIG. 6A, the horizontal axis corresponds to time,increasing from left to right and the vertical axis corresponds tofrequency. The various blocks shown in the figure represent DL BWPs. Afirst DL BWP is CORESET 0 610, which is shown to include a PDCCH 612. Asecond DL BWP is an INACTIVE DL BWP 620, which is shown to include aPDSCH 622. A further occurrence of CORESET 0 630 is also shown in thefigure.

In FIG. 6A, the condition for switching is met because the INACTIVE DLBWP 620 does not include all RBs of CORESET 0 610. Because the INACTIVEDL BWP 620 does not include all RBs of CORESET 0 610, a proper value ofK0 i.e. K0=5, which is greater than the switching delay, is used by thebase station because the base station also knows that the switchingcondition is met, and the base station should allow enough time to theUE to perform the switching. K0 indicates an offset (for example innumber of slots) between a slot where PDCCH that contains the DCI isreceived and a slot where the PDSCH is scheduled.

FIG. 6B illustrates an example of when a condition for DL BWP switchingis not met in the RRC_INACTIVE state, for example with respect to thesecond condition. In FIG. 6B, the horizontal axis corresponds to time,increasing from left to right and the vertical axis corresponds tofrequency. A first DL BWP is CORESET 0 610, which is shown to include aPDCCH 612. A second DL BWP is an INACTIVE DL BWP 620, which is shown toinclude a PDSCH 622.

In FIG. 6B, the condition for switching is not met because the INACTIVEDL BWP 620 includes all RBs of CORESET 0 610.

A switching delay that defines the delay between switching from one BWPto another BWP may be applied. In some embodiments, such a switchingdelay may be based on a value set out in a telecommunications standarddocument.

Embodiment 3-2

In some embodiments, a UE is provided with a predetermined delay, calledBWP switching delay, to accommodate switching of DL (or UL BWP), beforereceiving DL data in the RRC_INACTIVE state (or transmitting UL data inthe RRC_INACTIVE state). In some embodiments, the BWP switching delaymay be set forth in a telecommunications standard document. A possiblebenefit of these embodiments is to provide enough time for the UE toperform operations that are necessary for the UE to switch its DL (or ULBWP) in RRC_INACTIVE state.

Two examples of DL scheduling are DCI based DL scheduling and pagingbased DL scheduling.

FIG. 7 is a signaling flow diagram 700 showing signaling for DCI-basedDL data scheduling that occurs between a UE 701 and base station 702when the UE 701 is initially in an RRC_CONNECTED state 705 and then theUE 701 is released and enters an RRC_INACTIVE state 707.

Initially the UE 701 is in the RRC_CONNECTED state 705. The base station702 sends 710 an INACTIVE DL BWP configuration to the UE 701. At asubsequent point in time, the base station 702 sends 715 an RRCreleasefor suspension of connection to the UE 701. After receiving the release,the UE 701 transitions to the RRC_INACTIVE state 707. While the UE is inthe RRC_INACTIVE state 707, the base station 702 sends 720 a DCI inCORESET 0 scheduling DL data. Upon receipt of the DCI, the UE 701switches 725 to an INACTIVE DL BWP, if a switching condition is met. Thebase station 702 sends 730 DL data in the INACTIVE DL BWP. Once the DLdata has been received, the UE 801 switches 735 the DL BWP from INACTIVEDL BWP to CORESET 0, if the switching was performed in 725.

The UE 701 is in the inactive state when the DCI is received. In someinstances, the DCI includes a CRC scrambled with a RNTI that is specificto the UE 701 and to the inactive state. A RNTI that is specific to aparticular UE and to the inactive state is referred herein to as an“I-RNTI”. Because the I-RNTI is specific to the inactive state, theI-RNTI is not used to scramble the CRC of DCI for a connected or idlestate. In some implementations, the UE 701 is in the RRC_INACTIVE stateand the DCI is in the DCI format 1_0. The DCI includes a CRC that isscrambled with the I-RNTI of the UE 701. The I-RNTI is different from aPaging RNTI (P-RNTI), and is not used to scramble the CRC of DCI whenthe UE 701 is in the RRC_CONNECTED or RRC_IDLE states.

A UE in an inactive state monitors for DCI having a CRC scrambled withits own I-RNTI. The UE stores its own I-RNTI, and therefore this UE isable to descramble the CRC, and use the CRC to check if decoding of theDCI was successful. Because an I-RNTI is specific to a particular UE,any other UEs in the same network or service area will have a differentI-RNTI. The other UEs might not store the I-RNTI of the particular UE,and therefore the other UEs might not be able to descramble the CRC ofthe DCI.

The DCI includes a resource allocation in a resource allocation bitfield for the data transmission. In this way, the DCI could be orinclude a notification of data scheduling.

Based on the resource allocation, the UE 701 could receive the scheduleddata transmission on the PDSCH. The UE 701 is in the inactive state whenthe data transmission is received. The data transmission could be aunicast transmission or a multicast transmission.

Paging messages can be used by a network to facilitate a UE transitionto a connected state from an idle state or from an inactive state. Thepaging messages can be received over a paging physical DL shared channel(paging PDSCH), for example. The network initiates a paging procedure bytransmitting a paging message at a UE's paging occasion. The network mayaddress multiple UEs using a single paging message by including multipleUE identities (IDs) in a paging record that is carried by the pagingmessage. A paging record is a set of UE IDs that correspond to UEs beingpaged by the network. In 3GPP NR Specification #TS38.331, an example ofa paging record is the PagingRecord parameter and an example of a UE IDis the UE-Identity parameter.

According to an aspect of the present disclosure, a unicast or multicastdata transmission to or from a UE in an inactive state is scheduledthrough paging. The UE can be notified of the data transmission using anindication in paging DCI or in a paging message. The data transmissioncan then be received in the paging message or in a further transmissionthat is scheduled by the paging message.

In some embodiments, a UE in an idle or inactive state monitors a pagingsearch space for a physical DL control channel (PDCCH) containing pagingDCI. An example of paging DCI in NR is DCI format 1_0 having a cyclicredundancy check (CRC) scrambled or masked with the P-RNTI. UEs in anidle or inactive state know the P-RNTI, and therefore these UEs are ableto descramble or demask the CRC, and use the CRC to check if decoding ofthe DCI format 1_0 was successful. The DCI format 1_0 includes, amongother information, either or both of a short message and schedulinginformation for a paging message. The scheduling information for thepaging message could include a resource assignment with a frequencydomain resource assignment, a time domain resource assignment, a virtualresource block (VRB)-to-physical resource block (PRB) mapping, amodulation and coding scheme (MCS), and/or transport block (TB) scaling.By way of example, DCI format 1_0 having a CRC scrambled by the P-RNTIcould include any or all of the following bit fields:

-   -   Short message indicator—2 bits in length;    -   Short message—8 bits in length;    -   Frequency domain resource assignment for a paging message—┌log₂        (N_(RB) ^(DL,BwP)(N_(RB) ^(DL,BWP)+1)/2)┐ bits in length, where        N_(RB) ^(DL,BWP) could be equal to the size of the control        resource set (CORESET) 0 (if only the short message is carried,        then this bit field is reserved);    -   Time domain resource assignment for the paging message—4 bits in        length (if only the short message is carried, this bit field is        reserved);    -   VRB-to-PRB mapping for the paging message—1 bit in length (if        only the short message is carried, this bit field is reserved);    -   MCS for the paging message—5 bits in length (if only the short        message is carried, this bit field is reserved);    -   TB scaling for the paging message—2 bits in length (if only the        short message is carried, this bit field is reserved); and    -   Reserved bits—6 bits in length.

In the case that paging DCI contains a resource allocation for a pagingmessage, a UE that receives the paging DCI proceeds to receive thescheduled paging message based on the resource allocation. When a UE inan idle state receives a paging message, the UE may determine if any ofthe UE IDs included in each paging record of the paging message matchthe particular ID allocated to the UE by upper layers of the network. InNR, 5G-S-TMSI is used as the UE ID for paging a UE in RRC_IDLE state. Inthe case that a UE ID in a paging record matches the particular ID ofthe UE, then the UE may initiate a connection to the network, i.e.transition to a connected state, by forwarding the UE's particular IDand an access type, if present, to the upper layers. An access type fora UE may be included as the accessType parameter be included in 3GPP NRSpecification #TS38.331.

When a UE in an inactive state receives a paging message, the UE maydetermine if the UE ID included in each paging record of the pagingmessage matches the UE's stored FulII-RNTI. The FulII-RNTI is a 40-bitstring that is configured to the UE during an RRC suspension procedure.For example, according to 3GPP NR Specification #TS38.331, theFulII-RNTI could be configured in the SuspendConfig field of anRRCRelease information element (IE), which is configured to the UE forsuspension of the RRC connection and transition of the UE from theRRC_CONNECTED state to RRC_INACTIVE state.

Conventional control signaling mechanisms do not support (non-paging) DLdata transmission to a UE or data transmission from a UE in an inactivestate, except for transmissions that are done as part of statetransition procedure from an inactive to connected state. According tothese conventional control signaling mechanisms, when a UE is in aninactive state and is not performing a procedure for connectionresumption, the only DCI format that the UE monitors is the paging DCI.For example, the only DCI format that a UE in the RRC_INACTIVE statemonitors is DCI format 1_0 having a CRC scrambled by the P-RNTI.However, a conventional paging DCI does not support:

-   -   non-paging DL data scheduling;    -   notifications for non-paging DL data scheduling;    -   SL data scheduling; or    -   UL data scheduling.

FIG. 8 is a signaling flow diagram 800 showing signaling forpaging-based DL data scheduling that occurs between a UE 801 and basestation 802 when the UE 801 is initially in an RRC_CONNECTED state 805and then the UE 801 is released and enters an RRC_INACTIVE state 807.

Initially the UE 801 is in the RRC_CONNECTED state 805. The base station802 sends 810 an INACTIVE DL BWP configuration to the UE 801. At asubsequent point in time the base station 802 sends 815 an RRCreleasefor suspension of connection to the UE 801. After receiving the releasethe UE 801 transitions to the RRC_INACTIVE state 807. While the UE 801is in the RRC_INACTIVE state 807, the base station 802 sends 820 a DCIin CORESET 0 scheduling paging. The base station 802 then sends 822 apaging message in CORESET 0 that includes scheduling information for DLdata. Upon receipt of the paging message, the UE 801 switches 825 to anINACTIVE DL BWP, if a switching condition is met. The base station 802sends 830 DL data in the INACTIVE DL BWP. Once the DL data has beenreceived, the UE 801 switches 835 the DL BWP from INACTIVE DL BWP toCORESET 0, if the switching was performed in 825.

FIG. 9 is a signaling flow diagram 900 showing signaling for UL datatransmission in an INACTIVE UL BWP that occurs between a UE 901 and basestation 902 when the UE 1001 is initially in an RRC_CONNECTED state 905and then the UE 901 is released and enters an RRC_INACTIVE state 907.

Initially the UE 901 is in the RRC_CONNECTED state 905. The base station902 sends 910 an INACTIVE UL BWP configuration to the UE 901. At asubsequent point in time the base station 902 sends 915 an RRCreleasefor suspension of connection to the UE 901. After receiving the releasethe UE 901 transitions to the RRC_INACTIVE state 907. While the UE is inthe RRC_INACTIVE state 907, the UE 901 switches 920 to an INACTIVE ULBWP, if a switching condition is met. The UE 901 sends 925 UL data inthe INACTIVE DL BWP. Once the DL data has been sent, the UE 901 switches930 the UL BWP from INACTIVE UL BWP to the Initial BWP, if the switchingwas performed in 920.

In the case of DCI based DL scheduling, a UE may obtain the resourceassignment (RA) by decoding a DCI received in a PDCCH. A starting timefor BWP switching may be the end of k^(th) symbol of slot n containingthe PDCCH. The value of k may be predefined, e.g. k=3 or the value maybe configured by higher layers.

If a UE detects a DCI in a PDCCH which schedules unicast/multicast PDSCHfor the UE in the RRC_INACTIVE state and the DL BWP switching conditionin the RRC_INACTIVE state is met, the UE is not required to receive ortransmit in the cell during a time duration from the end of the k^(th)symbol of a slot where the UE receives the PDCCH until the beginning ofa slot indicated by the slot offset value of the time domain resourceassignment field in the DCI.

If a UE detects a DCI in a PDCCH which schedules unicast/multicast PUSCHfor the UE in the RRC_INACTIVE state and the UL BWP switching conditionin the RRC_INACTIVE state is met, the UE is not required to receive ortransmit in the cell during a time duration from the end of the k^(th)symbol of a slot where the UE receives the PDCCH until the beginning ofa slot indicated by the slot offset value of the time domain resourceassignment field in the DCI.

Therefore, if the switch to a new BWP occurs, the UE expects thecorresponding PDSCH to be scheduled on or after the slot n plus theappropriate delay, i.e. n+T_(INACTIVE_BWPswitchDelay), whereT_(INACTIVE_BWPswitchDelay) is defined in number of slots, and may bepredefined or configured to the UE by higher layers.

The UE will behave in a particular manner for DCI-based DL scheduling,when the DL BWP switching condition in the RRC_INACTIVE state is met.

After the UE receives a DL scheduling PDCCH at DL slot n, the UE canreceive PDSCH on the INACTIVE DL BWP on the first DL slot right afterthe beginning of DL slot n+T_(INACTIVE_BWPswitchDelay), whereT_(INACTIVE_BWPswitchDelay) is the DL BWP switching delay in number ofslots.

Referring back to the example of FIG. 6A, slot n is illustrated at thePDCCH 612 within CORESET 0 610 and the T_(INACTIVE_BWPswitchDelay) isshown to be 4 slots.

The UE, when in the RRC_INACTIVE state, does not expect a time domainresource assignment field providing a slot offset value for a PDSCHreception that is smaller than a predetermined delay used by the UE forDCI-based active DL BWP change. The time domain resource assignmentfield may be detected as part of the DCI format 1_0 having a CRCscrambled by I-RNTI. In the example of FIG. 6A, a time-domain resourceassignment offset of K0 satisfies a DL BWP switching delay used by theUE for DCI-based active DL BWP change, becauseK0>T_(INACTIVE_BWPswitchDelay).

In the case of paging based DL scheduling, when the UE obtains theresource assignment by decoding the paging payload, the UE may need sometime to process the paging transport block (TB) and obtain the resourceassignment. A starting symbol/slot for BWP switching may be the firstsymbol of a slot n with T_(PagingProcessingDelay) offset from the lastslot n containing the DL scheduling command (i.e. paging TB) i.e.

${n + \frac{T_{Pa{ging}\mspace{11mu}{Processing}\mspace{11mu}{Delay}} + T_{{{INACTIVE}\_{BWP}}\mspace{11mu}{switch}\mspace{11mu}{Delay}\mspace{11mu}{Paging}}}{{NR}\mspace{14mu}{Slot}\mspace{14mu}{length}}},$

where T_(PagingProcessingDelay) and T_(INACTIVE_BWPswitchDelayPaging)are in milliseconds.

The value of T_(PagingProcessingDelay) may be predefined or configuredto the UE by higher layers.

The UE will behave in a particular manner for Paging-based DLscheduling, when the DL BWP switching condition in the RRC_INACTIVEstate is met.

After the UE receives a DL scheduling paging message, the UE may be ableto receive PDSCH on the INACTIVE DL BWP on the first DL slot right afterthe beginning of DL slot

${n + \frac{T_{Pa{ging}\mspace{11mu}{Processing}\mspace{11mu}{Delay}} + T_{{{INACTIVE}\_{BWP}}\mspace{11mu}{switch}\mspace{11mu}{Delay}\mspace{11mu}{Paging}}}{{NR}\mspace{14mu}{Slot}\mspace{14mu}{length}}},$

where the DL slot n is the last slot containing the paging message,T_(PagingProcessingDelay) in milliseconds is the length of pagingprocessing delay, and T_(INACTIVE_BWPswitchDelayPaging) in millisecondsis the time used by the UE to perform BWP switching in the RRC_INACTIVEstate, and “NR Slot length” is the slot length in milliseconds of thenumerology of the paging message or a larger value between that of apaging SCS and a SCS of the INACTIVE DL BWP.

The UE, when in the RRC_INACTIVE state, does not expect a time domainresource assignment field in a paging message that includes a slotoffset value for a PDSCH reception that is smaller than a predetermineddelay used by the UE for a paging-based active DL BWP change.

Embodiment 3-3

According to another aspect of the disclosure, there is provided amechanism for autonomous DL BWP switching after receiving DL data in theRRC_INACTIVE state.

In some embodiments, the UE switches back to CORESET 0 after receivingthe PDSCH.

A switching delay may be included for the autonomous switching. Theswitching delay is considered as an offset from the last slot ncontaining the DL PDSCH.

The switching delay may have components that include a PDSCH processingdelay T_(INACTIVE_PDSCHprocessingDelay) and a DL BWP switching delayT_(INACTIVE_BWPswitchDelayPDSCH).

When the DL BWP switching condition in the RRC_INACTIVE state is met,after the UE receives DL PDSCH, the UE can receive PDSCH/PDCCH onCORESET 0 on the first DL slot right after the beginning of DL slot,i.e.

${n + \frac{T_{{{INACTIVE}\_{PDSCH}}\mspace{11mu}{processing}\mspace{11mu}{Delay}} + T_{{{INACTIVE}\_{BWP}}\mspace{11mu}{switch}\mspace{11mu}{Delay}\mspace{11mu}{PDSCH}}}{{NR}\mspace{14mu}{Slot}\mspace{14mu}{length}}},$

where the DL slot n is the last slot containing the PDSCH,T_(INACTIVE_PDSCHprocessingDelay) in milliseconds is the length of PDSCHprocessing delay, and T_(INACTIVE_BWPswitchDelayPDSCH) in millisecondsis the time used by the UE to perform BWP switching in the RRC_INACTIVEstate, and “NR Slot length” is the slot length in milliseconds of thenumerology of PDSCH or the larger value between a PDSCH SCS and a SCS ofCORESET 0.

Referring back to the example of FIG. 6A, a delay

$\frac{T_{{{INACTIVE}\_{PDSCH}}\mspace{11mu}{processing}\mspace{11mu}{Delay}} + T_{{{INACTIVE}\_{BWP}}\mspace{11mu}{switch}\mspace{11mu}{Delay}\mspace{11mu}{PDSCH}}}{{NR}\mspace{14mu}{Slot}\mspace{14mu}{length}}$

is shown from the start of the INACTIVE DL BWP before switching back toCORESET 0 630.

If UE receives unicast or multicast PDSCH in the RRC_INACTIVE state, theUE does not expect to transmit or receive during a time duration equalto a delay required by the UE for an active DL BWP change afterreceiving PDSCH from the end of the last slot containing the PDSCH.

Although DL and UL transmissions are described above, the datatransmission could instead be a SL transmission. A SL transmission couldbe transmitted or received by the UE on the physical SL shared channel(PSSCH).

FIG. 10 illustrates a flow chart 1000 for a method that may be used by aUE for downlink communications with a network device, uplinkcommunications with a network device or sidelink communications withanother UE.

At step 1010, while in a RRC_CONNECTED state, the UE determinesconfiguration information for configuring a BWP for communication in aRRC_INACTIVE state. In some embodiments, determining configurationinformation may involve the UE making an implicit determination of howthe UE should be configured based on information the UE is aware of. Insome embodiments, the configuration information may be derived frominformation the UE is aware of by indicating that the configured BWP fordownlink communication in the RRC_INACTIVE state is control resource set0 (CORESET 0) or may indicate that the configured BWP is a last activeBWP of the UE in the RRC_CONNECTED state before the UE enters theRRC_INACTIVE state. In some embodiments, the configuration informationmay be derived from information the UE is aware of by indicating thatthe configured BWP for uplink communication in the RRC_INACTIVE state isthe initial UL BWP or may indicate that the configured BWP is a lastactive BWP of the UE in the RRC_CONNECTED state before the UE enters theRRC_INACTIVE state.

In some embodiments, the determining configuration information mayinvolve the UE receiving explicit configuration information from thenetwork regarding how the UE should be configured. In some embodiments,when received by the UE, the configuration information may explicitlydefine BWP parameters for the configured BWP for communication in theRRC_INACTIVE state. In some embodiments, when received by the UE, theconfiguration information may indicate a BWP identifier that identifiesa previously configured BWP that will be used for communication in theRRC_INACTIVE state. In some embodiments, the configuration is receivedby the UE in ServingCellConfig parameter or in an RRCRelease messagesent as part of a suspension of the active RRC connection. In someembodiments, the configuration is received by the UE in a systeminformation block (SIB1) or a system information block other than SIB1for transmission in the RRC_CONNECTED state (SIBx).

At step 1020, the UE enters the RRC_INACTIVE state. In some embodiments,this is the result of the UE receiving signalling indicating asuspension of the RRC_CONNECTED state.

At step 1030, the UE using the configured BWP for communication in theRRC_INACTIVE state.

Step 1040 is an optional step that includes, when in the RRC_INACTIVEstate, the UE switching to the configured BWP for communication in theRRC_INACTIVE state. In some embodiments, the switching occurs when apre-defined condition is met. The pre-defined condition may be one of:the configured BWP for communication in the RRC_INACTIVE state has adifferent frequency location and bandwidth or a different sub-carrierspacing (SCS) or a different cyclic prefix (CP) than CORESET 0; or theconfigured BWP for communication in the RRC_INACTIVE state does notinclude all resource blocks of CORESET 0 or has a different SCS or adifferent CP than CORESET 0. The pre-defined condition may be one of:the configured BWP for communication in the RRC_INACTIVE state has adifferent frequency location and bandwidth or a different sub-carrierspacing (SCS) or a different cyclic prefix (CP) than the initial UL BWP;or the configured BWP for communication in the RRC_INACTIVE state doesnot include all resource blocks of the initial UL BWP or has a differentSCS or a different CP than the initial UL BWP.

In a further optional step 1050, when in the RRC_INACTIVE state, the UEswitches from the configured BWP for communication in the RRC_INACTIVEstate to CORESET 0 for DL or the initial UL BWP for UL.

Communication that may be received in the RRC_INACTIVE state may includedownlink control information that includes scheduling information forfurther communications. In some embodiments, the scheduling informationincludes scheduling information for receiving downlink data while in theRRC_INACTIVE state. In some embodiments, the scheduling informationincludes scheduling information for transmitting uplink data while inthe RRC_INACTIVE state.

In some embodiments, the configuration information for configuring theBWP for communication in the RRC_INACTIVE state includes an extended CP.The extended CP may be for an uplink BWP.

FIG. 11 illustrates a flow chart 1100 for a method that may be used by anetwork side device, such as a base station, for downlink communicationswith a UE or, uplink communications with a UE.

A first step 1105 includes the network side device determiningconfiguration information for configuring a bandwidth part (BWP) forcommunication in an RRC_INACTIVE state. The network side device and theUE operate in conjunction, so the network side device determines theconfiguration information so that the UE will be properly configured toreceive when the network side transmits. The network side device doesnot necessarily need to explicitly transmit the configurationinformation, as in optional step 1110 below, as the UE may be able toinfer the configuration information as described in various exampleearlier in the description.

Step 1110, that may be considered optional, involves a network sidedevice transmitting the configuration information for configuring theBWP for use by the UE for communication in the RRC_INACTIVE state. Insome embodiments, the configuration information may include explicitconfiguration information from the network regarding how the UE shouldbe configured. In some embodiments, the configuration information mayexplicitly define BWP parameters for the configured BWP forcommunication in the RRC_INACTIVE state. In some embodiments, theconfiguration information may indicate a BWP identifier that identifiesa previously configured BWP that will be used for communication in theRRC_INACTIVE state. In some embodiments, the configuration is receivedby the UE in ServingCellConfig parameter or in an RRCRelease messagesent as part of a suspension of the active RRC connection. In someembodiments, the configuration is received by the UE in a SIB1 or a SIBxother than SIB1.

At step 1120, the network side device transmits signalling indicating asuspension of an RRC_CONNECTED state resulting in the UE entering theRRC_INACTIVE state.

At step 1130, the network side device uses the configured BWP forRRC_INACTIVE state for communication with the UE when the UE is in theRRC_INACTIVE state.

Communication that may be received in the RRC_INACTIVE state may includedownlink control information that includes scheduling information forfurther communications. In some embodiments, the scheduling informationincludes scheduling information for receiving downlink data while in theRRC_INACTIVE state. In some embodiments, the scheduling informationincludes scheduling information for transmitting uplink data while inthe RRC_INACTIVE state.

In some embodiments, the configuration information for configuring theBWP for communication in the RRC_INACTIVE state includes an extended CP.The extended CP may be for an uplink BWP.

It should be appreciated that one or more steps of the embodimentmethods provided herein may be performed by corresponding units ormodules. For example, data may be transmitted by a transmitting unit ora transmitting module. Data may be received by a receiving unit or areceiving module. Data may be processed by a processing unit or aprocessing module. The respective units/modules may be hardware,software, or a combination thereof. For instance, one or more of theunits/modules may be an integrated circuit, such as field programmablegate arrays (FPGAs) or application-specific integrated circuits (ASICs).It will be appreciated that where the modules are software, they may beretrieved by a processor, in whole or part as needed, individually ortogether for processing, in single or multiple instances as required,and that the modules themselves may include instructions for furtherdeployment and instantiation.

Although a combination of features is shown in the illustratedembodiments, not all of them need to be combined to realize the benefitsof various embodiments of this disclosure. In other words, a system ormethod designed according to an embodiment of this disclosure will notnecessarily include all of the features shown in any one of the Figuresor all of the portions schematically shown in the Figures. Moreover,selected features of one example embodiment may be combined withselected features of other example embodiments.

Although this disclosure has been described with reference toillustrative embodiments, this description is not intended to beconstrued in a limiting sense. Various modifications and combinations ofthe illustrative embodiments, as well as other embodiments of thedisclosure, will be apparent to persons skilled in the art uponreference to the description. It is therefore intended that the appendedclaims encompass any such modifications or embodiments.

What is claimed is:
 1. A method comprising: receiving, by a userequipment (UE) in a RRC_CONNECTED state, a control message that releasesthe UE from the RRC_CONNECTED state and comprises configurationinformation for an uplink (UL) bandwidth part (BWP) for RRC_INACTIVEstate UL data communications; transitioning, by the UE in theRRC_CONNECTED state, to a RRC_INACTIVE state; and using, by the UE inthe RRC_INACTIVE state, the UL BWP for RRC_INACTIVE state UL datacommunications configured based on the configuration information.
 2. Themethod of claim 1, wherein the configuration information comprises BWPparameters for the UL BWP for RRC_INACTIVE state UL data communications.3. The method of claim 1, wherein the configuration informationcomprises a BWP identifier that identifies the UL BWP for RRC_INACTIVEstate UL data communications.
 4. The method of claim 1, wherein theconfiguration information indicates that the UL BWP for RRC_INACTIVEstate UL data communications is a last UL BWP that was used by the UEwhen the UE was in the RRC_CONNECTED state before the UE transitioned tothe RRC_INACTIVE state.
 5. The method of claim 1, further comprisingreceiving, by the UE in the RRC_INACTIVE state, downlink controlinformation (DCI) comprising scheduling information for RRC_INACTIVEstate UL data communications.
 6. The method of claim 1, wherein using,by the UE in the RRC_INACTIVE state, the UL BWP for RRC_INACTIVE stateUL data communications comprises transmitting UL data using the UL BWPconfigured based on the configuration information.
 7. The method ofclaim 1, wherein the configuration information comprises a subcarrierspacing (SPC), a cyclic prefix (CP), a frequency location, and abandwidth.
 8. The method of claim 7, wherein the CP is an extended CP.9. The method of claim 1, further comprising prior to using, by the UEin the RRC_INACTIVE state, the UL BWP for RRC_INACTIVE state UL datacommunications configured based on the configuration information,switching, by the UE in the RRC_INACTIVE state, from control resourceset 0 (CORSET 0) to the UL BWP for RRC_INACTIVE state UL datacommunications configured based on the configuration information. 10.The method of claim 9, wherein the switching occurs when a pre-definedcondition is met, wherein the pre-defined condition is one of: the ULBWP for RRC_INACTIVE state UL data communications has a differentfrequency location and bandwidth or a different sub-carrier spacing(SCS) or a different cyclic prefix (CP) than CORESET 0; or the UL BWPfor RRC_INACTIVE state UL data communications does not include allresource blocks of CORESET 0 or has a different SCS or a different CPthan CORESET
 0. 11. The method of claim 10, further comprisingswitching, by the UE in the RRC_INACTIVE state, from the BWP forRRC_INACTIVE state UL data communications to CORESET
 0. 12. The methodof claim 1, wherein the UL BWP is specific to the UE.
 13. The method ofclaim 1, wherein the UL BWP is a group specific UL BWP or acell-specific UL BWP.
 14. The method of claim 1, further comprising:receiving, by the UE in the RRC_CONNECTED state, second configurationinformation for a downlink (DL) bandwidth part (BWP) for RRC_INACTIVEstate DL data communications; and transitioning, by the UE in theRRC_CONNECTED state, to a RRC_INACTIVE state; and using, by the UE inthe RRC_INACTIVE state, the DL BWP for RRC_INACTIVE state UL DLcommunications configured based on the second configuration information.15. The method of claim 14, wherein the DL BWP is specific to the UE.16. The method of claim 14, wherein the DL BWP is a group specific DLBWP or a cell-specific DL BWP.
 17. A user equipment (UE) comprising: oneor more processors; and a non-transitory memory storing instructionswhich, when executed by the one or more processors configure the UE to:receive in a RRC_CONNECTED state, a control message that releases the UEfrom the RRC_CONNECTED state and comprises configuration information foran uplink (UL) bandwidth part (BWP) for RRC_INACTIVE state UL datacommunications; transition from the RRC_CONNECTED state to aRRC_INACTIVE state; and use, in the RRC_INACTIVE state, the UL BWP forRRC_INACTIVE state UL data communications configured based on theconfiguration information.
 18. The UE of claim 17, wherein theconfiguration information comprises BWP parameters for the UL BWP forRRC_INACTIVE state UL data communications.
 19. The UE of claim 17,wherein the configuration information comprises a BWP identifier thatidentifies the UL BWP for RRC_INACTIVE state UL data communications. 20.The UE of claim 17, wherein the configuration information indicates thatthe UL BWP for RRC_INACTIVE state UL data communications is a last ULBWP that was used by the UE when the UE was in the RRC_CONNECTED statebefore the UE transitioned to the RRC_INACTIVE state.
 21. The UE ofclaim 17, wherein the non-transitory memory stores further instructionswhich, when executed by the one or more processors configure the UE toreceive in the RRC_INACTIVE state, downlink control information (DCI)comprising scheduling information for RRC_INACTIVE state UL datacommunications.
 22. The UE of claim 17, wherein use, in the RRC_INACTIVEstate, of the UL BWP for RRC_INACTIVE state UL data communicationscomprises transmitting UL data using the UL BWP configured based on theconfiguration information.
 23. The UE of claim 17, wherein theconfiguration information comprises a subcarrier spacing, a cyclicprefix (CP), a bandwidth and a frequency location.
 24. The UE of claim23, wherein the CP is an extended CP.
 25. The UE of claim 17, whereinthe non-transitory memory stores further instructions which, whenexecuted by the one or more processors configure the UE to, prior to usein the RRC_INACTIVE state, of the UL BWP for RRC_INACTIVE state UL datacommunications configured based on the configuration information,switch, in the RRC_INACTIVE state, from control resource set 0 (CORSET0) to the UL BWP for RRC_INACTIVE state UL data communicationsconfigured based on the configuration information.
 26. The UE of claim25, wherein the switch occurs when a pre-defined condition is met,wherein the pre-defined condition is one of: the UL BWP for RRC_INACTIVEstate UL data communications has a different frequency location andbandwidth or a different sub-carrier spacing (SCS) or a different cyclicprefix (CP) than CORESET 0; or the UL BWP for RRC_INACTIVE state UL datacommunications does not include all resource blocks of CORESET 0 or hasa different SCS or a different CP than CORESET
 0. 27. The UE of claim26, wherein the non-transitory memory stores further instructions which,when executed by the one or more processors configure the UE to switch,in the RRC_INACTIVE state, from the BWP for RRC_INACTIVE state UL datacommunications to CORESET
 0. 28. The UE of claim 17, wherein the UL BWPis specific to the UE.
 29. The UE of claim 17, wherein the UL BWP is agroup specific UL BWP or a cell-specific UL BWP.
 30. The UE of claim 17,wherein the non-transitory memory stores further instructions which,when executed by the one or more processors configure the UE to: receivein the RRC_CONNECTED state, second configuration information for adownlink (DL) bandwidth part (BWP) for RRC_INACTIVE state DL datacommunications; and transition from the RRC_CONNECTED state toRRC_INACTIVE state; and use in the RRC_INACTIVE state, the DL BWP forRRC_INACTIVE state UL DL communications configured based on the secondconfiguration information.
 31. The UE of claim 30, wherein the DL BWP isspecific to the UE.
 32. The UE of claim 30, wherein the DL BWP is agroup specific DL BWP or a cell-specific DL BWP.